Changes are coming to https://stigviewer.com.
Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey
The Mainframe Product must generate audit records for all kernel module load, unload, and restart events, and for all program initiations.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
|---|---|---|---|---|
| V-205618 | SRG-APP-000510-MFP-000135 | SV-205618r961845_rule | Medium |
| Description |
|---|
| Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident, or identify those responsible for one. Audit records can be generated from various components within the information system (e.g., module or policy filter). |
| STIG | Date |
|---|---|
| Mainframe Product Security Requirements Guide | 2024-07-02 |
Details
| Check Text ( C-5884r300081_chk ) |
|---|
| Examine installation and configuration settings. Verify that the Mainframe Product identifies all Kernel module activities, writes to SMF, and/or uses an external security manager (ESM) to generate audit records for all kernel mode load, unload, and restart events, and for all program initiations. If it does not, this is a finding. |
| Fix Text (F-5884r300082_fix) |
|---|
| Configure the Mainframe Product to write to SMF and/or provide audit SAF call for all kernel module load, unload, and restart events, and for all program initiations. |